Method and apparatus for remotely debugging applications via a user terminal

ABSTRACT

An apparatus for and method of utilizing an internet terminal coupled to the world wide web to access an existing proprietary data base management system having a dialog-based request format. The user request is received by a web server from the world wide web and converted into one or more sequenced data base management commands. These data base management commands are sequentially presented to the data base management system and the intermediate products stored. A debug program located on the server side of the interface provides execution of sequenced data base management commands in a trace mode. The results and intermediate results are stored in a debug file for future access by a service developer at a user terminal.

CROSS REFERENCE TO CO-PENDING APPLICATIONS

U.S. patent application Ser. No. 09/164,759, filed Oct. 1, 1998, andentitled, “A Common Gateway Which Allows Applets to Make Program Callsto OLTP Applications Executing on an Enterprise Server”; U.S. patentapplication Ser. No. 09/164,932, filed Oct. 1, 1998, and entitled, “AMulti-Client User Customized DOM Gateway for an OLTP Enterprise ServerApplication”; U.S. patent application Ser. No. 09/164,908, filed Oct. 1,1998, and entitled, “An Automated Development System for DevelopingApplications that Interface with Both Distributed Component Object Model(DOM) and Enterprise Server Environments”; U.S. patent application Ser.No. 09/164,933, filed Oct. 1, 1998, and entitled, “Providing a ModularGateway Architecture Which Isolates Attributes of the Client and ServerSystems into Independent Components”; U.S. patent application Ser. No.09/164,822, filed Oct. 1, 1998, and entitled, “Making CGI Variables andCookie Information Available to an OLTP System”; U.S. patent applicationSer. No. 09/164,673, filed Oct. 1, 1998, and entitled, “A Gateway forDynamically Providing Web Site Status Information”; U.S. patentapplication Ser. No. 09/164,756, filed Oct. 1, 1998, and entitled,“Development System for Automatically Enabling a Server Application toExecute with an XATMI-complaint transaction MGR :Managing Transactionswithin Multiple Environments”; U.S. patent application Ser. No.09/189,053, filed Nov. 9, 1998, and entitled, “Cool ICE BatchInterface”; U.S. patent application Ser. No. 09/188,725, filed Nov. 9,1998, and entitled, “Cool ICE State Management”; U.S. patent applicationSer. No. 09/188,628, filed Nov. 9, 1998, and entitled, “Cool ICEWorkstation Directory/File Browser”; U.S. patent application Ser. No.09/188,840, filed Nov. 9, 1998, and entitled, “Cool ICE Icons”; U.S.patent application Ser. No. 09/188,738, filed November 9, 1998, andentitled, “Cool ICE Service Templates”; U.S. patent application Ser. No.09/189,383, filed Nov. 9, 1998, and entitled, “Automatic Footer Text onHTML Pages”; U.S. patent application Ser. No. 09/189,615, filed Nov. 9,1998, and entitled, “Availability Message”; U.S. patent application Ser.No. 09/189,611, filed Nov. 9, 1998, and entitled, “Cool ICE SystemSettings”; U.S. patent application Ser. No. 09/188,807, filed Nov. 9,1998, and entitled, “Cool ICE Service Handler”; and U.S. patentapplication Ser. No. 09/189,616, filed Nov. 9, 1998, and entitled,“Server Side Variables” are commonly assigned co-pending applicationsincorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to data base management systemsand more particularly relates to enhancements for providing access todata base management systems via internet user terminals.

2. Description of the Prior Art

Data base management systems are well known in the data processing art.Such commercial systems have been in general use for more than 20 years.One of the most successful data base management systems is availablefrom Unisys Corporation and is called the CLASSIC MAPPER®databasemanagement system. The CLASSIC MAPPER system can be reviewed using theCLASSIC MAPPER User's Guide which may be obtained from UnisysCorporation.

The CLASSIC MAPPER system, which runs on proprietary hardware alsoavailable from Unisys Corporation, provides a way for clients topartition data bases into structures called filing cabinets and drawers,as a way to offer a more tangible format. The Mapper data base managerutilizes various predefined high-level instructions whereby the database user may manipulate the data base to generate human-readable datapresentations called “reports”. The user is permitted to prepare listsof the various predefined high-level instructions into data base managerprograms called “Mapper Runs”. Thus, users of the CLASSIC MAPPER systemmay create, modify, and add to a given data base and also generateperiodic and aperiodic reports using various Mapper Runs.

However, with the CLASSIC MAPPER system, as well as with similarproprietary data base management systems, the user must interface withthe data base using a terminal coupled directly to the proprietarysystem and must access and manipulate the data using the Mapper Runcommand language of CLASSIC MAPPER. Ordinarily, that means that the usermust either be co-located with the hardware which hosts the data basemanagement system or must be coupled to that hardware through dedicatedtelephone, satellite, or other data links. Furthermore, the user usuallyneeds to be schooled in the command language of CLASSIC MAPPER (or otherproprietary data base management system) to be capable of generatingMapper Runs.

Since the advent of large scale, dedicated, proprietary data basemanagement systems, the internet or world wide web has come into being.Unlike closed proprietary data base management systems, the internet hasbecome a world wide bulletin board, permitting all to achieve nearlyequal access using a wide variety of hardware, software, andcommunication protocols. Even though some standardization has developed,one of the important characteristics of the world wide web is itsability to constantly accept new and emerging techniques within a globalframework. Many current users of the internet have utilized severalgenerations of hardware and software from a wide variety of suppliersfrom all over the world. It is not uncommon for current day youngchildren to have ready access to the world wide web and to havesubstantial experience in data access using the internet.

Thus, the major advantage of the internet is its universality. Nearlyanyone, anywhere can become a user. That means that virtually allpersons are potentially internet users without the need for specializedtraining and/or proprietary hardware and software. One can readily seethat providing access to a proprietary data base management system, suchas CLASSIC MAPPER, through the intemet would yield an extremelyinexpensive and universally available means for accessing the data whichit contains and such access would be without the need for considerablespecialized training.

There are two basic problems with permitting internet access to aproprietary data base. The first is a matter of security. Because theinternet is basically a means to publish information, great care must betaken to avoid intentional or inadvertent access to certain data byunauthorized intemet users. In practice this is substantiallycomplicated by the need to provide various levels of authorization tointemet users to take full advantage of the technique. For example, onemight have a first level involving no special security featuresavailable to any intemet user. A second level might be for specificcustomers, whereas a third level might be authorized only for employees.One or more fourth levels of security might be available for officers orothers having specialized data access needs.

Existing data base managers have security systems, of course. However,because of the physical security with a proprietary system, a certaindegree of security is inherent in the limited access. On the other hand,access via the intemet is virtually unlimited which makes the securityissue much more acute.

The second major problem is imposed by the intemet protocol itself. Oneof the characteristics of the internet which makes it so universal isthat any single transaction in HTML language combines a single transfer(or request) from a user coupled with a single response from the intemetserver. In general, there is no means for linking multiple transfers (orrequests) and multiple responses. In this manner, the internet utilizesa transaction model which may be referred to as “stateless”. Thislimitation ensures that the intemet, its users, and its servers remainsufficiently independent during operation that no one entity or group ofentities can unduly delay or “hang-up” the communications system or anyof its major components. Each transmissions results in a termination ofthe transaction. Thus, there is no general purpose means to link datafrom one internet transaction to another, even though in certainspecialized applications limited amounts of data may be coupled using“cookies” or via attaching data to a specific HTML screen.

However, some of the most powerful data base management functions orservices of necessity rely on coupling data from one transaction toanother in dialog fashion. In fact this linking is of the essence ofMapper Runs which assume change of state from one command languagestatement to the next. True statelessness from a first Mapper command tothe next or subsequent Mapper command would preclude much of the powerof CLASSIC MAPPER (or any other modem data base management system) as adata base management tool and would eliminate data base management as wenow know it.

Not only is there a need to initiate and control the sequences ofcommand language script to perform the functions of the data basemanagement system, but to provide the internet user with a full range ofcapabilities, the user must be permitted to develop such sequences andstore them for future use. However, to develop the command languagescript sequences, the user must have a hither-to-unknown debug toolwhich operates over the world wide web.

SUMMARY OF THE INVENTION

The present invention overcomes the disadvantages of the prior art byproviding a method of and apparatus for utilizing the power of a fullfeatured data base management system by a user at a terminal coupled tothe world wide web or intemet. In order to permit any such access, thepresent invention must first provide a user interface, called a gateway,which translates transaction data transferred from the user over theintemet in HTML format into a format from which database managementsystem commands and inputs may be generated. The gateway must alsoconvert the data base management system responses and outputs into anHTML document for display on the user's intemet terminal. Thus, as aminimum, the gateway must make these format and protocol conversions. Inthe preferred embodiment, the gateway resides in the web server coupledto the user via the world wide web and coupled to proprietary data basemanagement system.

To make access to a proprietary data base by intemet users practical, asophisticated security system is required to prevent intentional orinadvertent unauthorized accesses. As discussed above, such a securitysystem should provide multiple levels of access to accommodate a varietyof authorized user categories. In the preferred embodiment of thepresent invention, several levels of data classification are providedand several classes of users are defined. This permits certain levels ofdata to be accessed by one or more of the several classes of user. Thesecurity system may either reside in the web server containing thegateway or may be an existing component of the data base managementsystem.

Whereas the gateway and the security system are the minimum necessary topermit the most rudimentary form of communication between the internetterminal of the user and the proprietary data base management system, asexplained above, the intemet is a “stateless” communication system; theaddition of the gateway and the security system do not change thisstatelessness. To unleash the real power of the database managementsystem, the communication protocol between the data base and the usermust permit the user to request, initiate, and control the complex database management functions available from the proprietary data basemanagement system.

The present invention provides the user with the opportunity to developand execute data base management services which consist of sequences ofscript in the command language of the data base management system. Thus,instead of considering each transfer from the internet user coupled withthe corresponding server response as an isolated transaction event asdefined by the world wide web, one or more related service requests maybe functionally associated in a service request sequence as defined bythe data base management system into a dialog.

A repository is established to store the script defining the servicerequest sequence for future reference. The repository can also storeintermediate requests and responses, as well as other data associatedwith the service request sequence. Thus, the repository bufferscommands, data, and intermediate products utilized in formattingsubsequent data base management service requests and in formattingsubsequent HTML pages to be displayed to the user.

The transaction data in HTML format received by the server from theuser, along with the state information stored in the repository, areprocessed by a service handler into a sequence of service requests inthe command language of the data base management system. Sequencing andcontrol of the data base management system is via an administrationmodule.

However, to develop the desired sequence of command language statements,the user needs to have a debug tool which permits a script sequence tobe executed under test conditions and which gives access to all of theintermediate products. This offers the user/developer opportunities totest and modify script sequences until the desired functionality hasbeen achieved and all bugs are removed.

Through the use of the repository to store the service request sequence,the service handler to generate data base management command language,and the administration module, the world wide web user is capable ofperforming each and every data base management function available to anyuser, including a user from a proprietary terminal having a dedicatedcommunication link which is co-located with the proprietary data basemanagement system hardware and software. In addition, the data basemanagement system user at the world wide web terminal is able toaccomplish this in the HTML protocol, without extensive trainingconcerning the command language of the data base management system.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects of the present invention and many of the attendantadvantages of the present invention will be readily appreciated as thesame becomes better understood by reference to the following detaileddescription when considered in connection with the accompanyingdrawings, in which like reference numerals designate like partsthroughout the figures thereof and wherein:

FIG. 1 is pictographic view of the COOL ICE system coupled between auser on the world wide web and an existing proprietary data basemanagement system;

FIG. 2 is a schematic drawing showing the operation of a multi-levelsecurity system in accordance with the preferred embodiment of thepresent invention;

FIG. 3 is a pictographic view of the hardware of the preferredembodiment;

FIG. 4 is a semi-schematic diagram of the operation of the COOL ICEsystem;

FIG. 5 is an overall schematic view of the software of the COOL ICEsystem;

FIG. 6 is a schematic view of a service request;

FIG. 7 shows a schematic view of a service request sequence;

FIG. 8 is a diagrammatic comparison between a dialog-based structure anda service-based structure;

FIG. 9 is a detailed diagram of a debug operation utilizing the debugtool of the present invention;

FIG. 10 is a view of the windows accessed to review the trace log; and

FIG. 11 is a view of the windows utilized in referencing the trace logfor debug purposes.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention is described in accordance with several preferredembodiments which are to be viewed as illustrative without beinglimiting. These several preferred embodiments are based upon Series 2200hardware and operating systems, the CLASSIC MAPPER data base managementsystem, and the COOL ICE software components, all available from UnisysCorporation.

FIG. 1 is an overall pictographic representation of a system 10permitting access to a proprietary data base management system via anintemet terminal. Existing data bases and applications 12 representscommercially available hardware and software systems which typicallyprovide select users with access to proprietary data and data basemanagement functions. In the preferred embodiment, existing data basesand applications 12 represents Series 2200 hardware and operating systemcontaining one or more data bases prepared using CLASSIC MAPPER database management system, all available from Unisys Corporation.Historically, existing data bases and applications 12 could only beaccessed from a dedicated, direct terminal link, either physicallyco-located with the other system elements or connected thereto via asecured dedicated telephonic, satellite, or fiber optic link.

With the preferred mode of the present invention, communication betweennew web application terminal 14 and existing data bases and applications12 is facilitated. As discussed above, this permits nearly universalaccess by users world wide without specialized hardware and/or usertraining. The user effects the access using standardized HTMLtransaction language through world wide web link 16 to the COOL ICEsystem 20, which serves as a world wide web server to world wide weblink 16.

COOL ICE system 20 appears to existing data bases and applications 12 asa data base management system proprietary user terminal over dedicatedlink 18. Oftentimes, dedicated link 18 is an intranet or other localizednetwork link. COOL ICE system 20 is currently available in commercialform without the present invention as COOL ICE Revision Level 1.1 fromUnisys Corporation.

FIG. 2 is a schematic diagram of security system 22 of the preferredmode of the present invention. By way of example, there are fourcategories of service defined, each with its own functionality andportion of the data base. Service A 36 contains data and functions whichshould only be made available to customers. Service B 38 contains dataand functions which should only be made available to customers oremployees. Service C 40 contains data and functions which should only bemade available to employees, and Service D 42, containing the leastrestrictive data and functions may be made available to anyone,including the general public.

In a typical application, Service D 42 might contain the general homepage information of the enterprise. It will consist of only the mostpublic of information. It is likely to include the name, address, e-mailaddress, and phone number of the enterprise, along with the most publicof the business details. Usually, Service D 42 would include means ofpresenting the information in a sufficiently interesting way to enticethe most casual of the public user to make further inquiry and thusbecome more involved with the objectives of the enterprise. Service D 42represents the lowest level of security with data and functionsavailable to all.

Service C 40 is potentially the highest level of classification. Itcontains data and functions which can be made available only toemployees. In actual practice, this might entail a number of sub levelscorresponding to the various levels of authority of the variousemployees. However, some services may be so sensitive that theenterprise decides not to provide any access via the internet. Thismight include such things as strategic planning data and tools, advancedfinancial predictions, specific information regarding individualemployees, marketing plans, etc. The penalty for this extreme securitymeasure is that even authorized individuals are prohibited fromaccessing these services via the internet, and they must take thetrouble to achieve access via an old-fashioned dedicated link.

Customers and employees may share access to Service B 38. Nevertheless,these data and functions are sufficiently sensitive that they are notmade public. Service B 38 likely provides access to productspecifications, delivery schedules and quantities, and pricing.

For customer access only is Service A 36. One would expect marketinginformation, along with specific account information, to be availablehere.

These four service levels (i.e., Service A 36, Service B 38, Service C40, and Service D 42) are regulated in accordance with three securityprofiles. The lowest level of security does not require a securityprofile, because any member of the general public may be granted access.This can be readily seen as guest category 28 (e.g., a member of thepublic) can directly access Service D 42. Of course, all othercategories of user may also directly access Service D 42, because allmembers of the more restrictive categories (e.g., customers andemployees) are also members of the general public (i.e., the leastrestrictive category).

Security Profile #1, 30 permits access to Service A 36 if and only ifthe requester seeking access is a customer and therefore a member ofcustomer category 24. Members of customer category 24 need to identifythemselves with a customer identification code in order to gain access.The assigning and processing of such identification codes are well knownto those of skill in the art.

Similarly, Security Profile #3, 34 permits access to Service C 40 if andonly if the requestor seeking access is an employee and therefore amember of employee category 26. Security Profile #2, 32 permits accessto Service B 38 to requestors from either customer category 24 oremployee category 26, upon receipt of a customer identification code oran employee identification code.

FIG. 3 is a pictorial diagram of hardware suite 44 of the preferredembodiment of the present invention. The client interfaces with thesystem via internet terminal 64. Preferably, internet terminal 64 is anindustry compatible, personalized computer having a current version ofthe Windows operating system and suitable web browser, all being readilyavailable commercial products. Internet terminal 64 communicates overworld wide web access 48 using standardized HTML protocol.

The COOL ICE system is resident in web server 50, which is coupled tointernet terminal 46 via world wide web access 48. In the preferredmode, web server 50 is owned and operated by the enterprise owning andcontrolling the proprietary data base management system. Web server 50may serve as the internet access provider for intemet terminal 46wherein world wide web access 48 is typically a dial-up telephone line.This would ordinarily be the case if the shown client were an employeeof the enterprise. On the other hand, web server 50 may be a remoteserver site on the internet if the shown client has a different internetaccess provider. This would ordinarily occur if the shown client were acustomer or guest.

In addition to being coupled to world wide web access 48, web server 50,containing the COOL ICE system, is coupled to intranet 52 of theenterprise as shown. Intranet 52 provides the enterprise withcommunication for its internal business purposes. This communication isadministered and managed by enterprise server 54 having enterpriseserver storage facility 56. Thus, employees and others granted accessmay communicate via intranet 52 within the physical security provided bythe enterprise. Also coupled to intranet 52 is departmental server 58having departmental server storage facility 60. Additional departmentalservers (not shown) may be coupled to intranet 52. The enterprise dataand enterprise data base management service functionality typicallyresides within enterprise server 54, departmental server 58, and anyother departmental servers (not shown). Normal operation in accordancewith the prior art would provide access to this data and data basemanagement functionality via intranet 52 to users directly coupled tointranet 52.

In the preferred mode of the present invention, access to this data anddata base management functionality is also provided to users (e.g.,intemet terminal 64) not directly coupled to intranet 52, but indirectlycoupled to intranet 52 via web server 50. As explained below in moredetail, web server 50 provides this access utilizing the COOL ICE systemresident in web server 50.

FIG. 4 is pictographic view of the system of FIG. 3 with particulardetail showing the organization and operation of the COOL ICE system 20,which is resident in the web server (see also FIG. 3). In this view, theclient accesses the data base management system within the enterprisevia intemet terminal 64 which is coupled to the web server 50 by worldwide web path 66. Again, the internet terminal 64 is preferably anindustry standard computer utilizing a commercially available webbrowser.

The basic request/response format of the COOL ICE system involves a“service” (defined in greater detail below) which is an object of theCOOL ICE system. The service is a predefined operation or relatedsequence of operations which provide the client with a desired static ordynamic result. The services are categorized by the language in whichthey were developed. Whereas all services are developed with client-sidescripting which is compatible with internet terminal 64 (e.g., HTML),the server-side scripting defines the service category. Native servicesutilize COOL ICE script for all server-side scripting. On the otherhand, open services may have server-side scripting in a variety ofcommon commercial languages including Jscript, VBScript, ActiveXcontrols, and HTML. Because native services are developed in the COOLICE language, greater development flexibility and variety are availablewith this technique.

Web server 50 provides open server processor 70 for Active Server Pages(ASP's) which have been developed as open services and Default ASPprocessor 72 for native services. After the appropriate decoding (i.e.,native or open service), a call to the corresponding COOL ICE object 74is initiated as shown. The selected object is processed by COOL ICEengine 76.

Repository 80 is a storage resource for long term storage of the COOLICE objects and short term storage of the state of a particular service.Further details concerming repository 80 may be found by consulting theabove referenced, commonly-assigned, co-pending U.S. Patent Application.In the preferred mode of the present invention, the objects stored inrepository 80 are typically very similar to mapper runs as describedabove. For a more detailed description of mapper runs, CLASSIC MAPPERUser Manual is available from Unisys Corporation and incorporated hereinby reference. In the more general case, repository 80 would typicallystore predefined sequences of statements in the command language of theenterprise data base management system(s) to be accessed.

COOL ICE engine 52 sequences these previously stored command statementsand uses them to communicate via intranet 84 with the data basemanagement system(s) (e.g., CLASSIC MAPPER) resident on enterpriseserver 54 and departmental server 58. The short term storage capabilityof repository 80 is utilized by COOL ICE engine 76 to store the stateand intermediate products of each service until the processing sequencehas been completed. Following completion, COOL ICE engine 76 retrievesthe intermediate products from repository 80 and formats the outputresponse to the client, which is transferred to internet terminal 64 viaweb server 58 and world wide web path 66.

COOL ICE Administrator 104 is available for coordination of theoperation of COOL ICE system 20 and thus can resolve conflicts, setrun-time priorities, deal with security issues, and serve as adevelopmental resource. Graphing engine 78 is available to efficientlyprovide graphical representations of data to be a part of the responseof a service. This tends to be a particularly useful utility, becausemany of the existing data base management systems have relatively sparseresources for graphical presentation of data.

The combination of COOL ICE engine 76 and repository 80 permits a rathersimplistic service request from internet terminal 64 in dialog format toinitiate a rather complex series of data base management systemfunctions. In doing so, COOL ICE engine 76 emulates an intranet user ofthe data base management system(s) resident on enterprise server 54and/or departmental server 58. This emulation is only made possible,because repository 80 stores sequences of command language statements(i.e., the logic of the service request) and intermediate products(i.e., the state of the service request). It is these functions whichare not available in ordinary dialog on the world wide web and aretherefore not even defined in that environment.

FIG. 5 is a schematic diagram 90 of the software components of the COOLICE system and the software components to which it interfaces in thepreferred mode of the present invention. The client user of the COOL ICEsystem interfaces directly with web browser 92 which is resident oninternet terminal 64 (see also FIG. 4). Web browser 92 is a commerciallyavailable browser operating under a current version of the Windowsoperating system (e.g., Windows 95). The only special requirement of webbrowser 92 is that it be capable of supporting frames.

Web browser 92 communicates with web server software 96 via internetstandard protocol using HTML language using world wide web path 94. Webserver software 96 is also commercially available software, which is, ofcourse, appropriate for to the web server host hardware configuration.In the preferred mode of the present invention, web server software 96is hosted on a Series 2200 mainframe available from Unisys Corporation,from which web server software 96 is readily available.

COOL ICE system software 98 consists of COOL ICE Gateway 100, COOL ICEservice handler 102, COOL ICE administration 104, COOL ICE repository106, and COOL ICE scripting 108. It is these five software modules whichinterface to web server software 96 in HTML using a dialog format andinterface to data base management system interconnect 110 in the commandlanguage of the enterprise data base management system(s) (i.e., CLASSICMAPPER in the preferred mode of the present invention).

COOL ICE gateway 100 is the interface between standard, commerciallyavailable, web server software 96 and the internal COOL ICE systemlanguage and logic. As such, COOL ICE gateway 100 translates the dialogformat, incoming HTML service request into internal COOL ICE languageand protocol. Intrinsic in this translation is a determination of theserve category (see also FIG. 4)—that is whether the service request isa native service (i.e., with COOL ICE server-side scripting) or an openservice (i.e., with server-side scripting in another commerciallanguage).

The service request, received from COOL ICE gateway 100, is utilized byCOOL ICE service handler 102 to request the corresponding object fromCOOL ICE repository 106 and to open temporary state storage using COOLICE repository 106. COOL ICE scripting 108 is called to translate theserver-side scripting of an open service request as necessary. COOL ICEservice handler 102 sequences through the command language statements ofthe object received from COOL ICE repository 106 and forwards eachcommand in turn to data base management system software 114 foraccessing of the enterprise proprietary data base management system.COOL ICE service handler 102 receives each of the intermediate productsfrom data base management system software 114 and transfers each to COOLICE repository 106 for temporary storage until completion of the servicerequest. COOL ICE service handler 102 retrieves the intermediateproducts from COOL ICE repository 106 upon completion of the servicerequest and formulates the COOL ICE response for transfer to browser 92via web server software 96 and world wide web path 94.

COOL ICE administration 104 implements automatic and manual control ofthe process. It provides for record keeping, for resolution of certainsecurity issues, and for development of further COOL ICE objects.Interconnect 110 and interconnect 112 are software interface modules forcommunicating over the enterprise intranet (see also FIG. 4). Thesemodules are dependent upon the remaining proprietary hardware andsoftware elements coupled to the enterprise intranet system. In thepreferred mode of the present invention, these are commerciallyavailable from Unisys Corporation.

FIG. 6 is a schematic diagram 116 showing the processing of a servicerequest by the COOL ICE system. Screen 118 is the view as seen by theclient or user at an internet terminal (see also FIG. 4). This screen isproduced by the commercially available browser 92 selected by the user.Any such industry standard browser is suitable, if it has the capabilityto handle frames. The language of screen 118 is HTML 124. Hyperlinks 126is used in locating the URL of the COOL ICE resident server. In manyinstances, this will simply be the internet access provider of theintemet terminal, as when the intemet terminal is owned by theenterprise and the user is an employee. However, when the user is not anemployee and the internet terminal is not necessarily owned by theenterprise, it becomes more likely that hyperlinks 126 identifies aremotely located server.

Icon 122 is a means of expressly identifying a particular servicerequest. Such use of an icon is deemed to be unique. Additional detailconcerning this use of an icon is available in the above identified,commonly assigned, co-pending U.S. Patent application. Window area 128provides for the entry of any necessary or helpful input parameters. Notshown are possible prompts for entry of this data, which may be definedat the time of service request development. Submit button provides theuser with a convenient means to transmit the service request to the webserver in which the COOL ICE system is resident.

Upon “clicking on” submit button 130, screen 118 is transmitted to webserver 50 via world wide web path 132. As discussed above, world wideweb path 132 may be a telephonic dial-up of web server 50 or it might bea long and complex path along the internet if web server 50 is remotefrom the originating internet terminal. Web server 50 is the softwarewhich performs the retrieval of screen 118 from world wide web path 132.

Screen 118 is transferred from web server 50 to COOL ICE gateway 100,wherein it is converted to the internal COOL ICE protocol and language.A browser input file is opened at storage resource 146 via path 140.Thus the initial service request can be accessed from storage resource146 during processing up until the final result is transferred back tothe user. This access readily permits multi-step and iterative servicerequest processing, even though the service request was transferred as asingle internet dialog element. This storage technique also providesinitially received input parameters to later steps in the processing ofthe service request.

COOL ICE gateway 100 notifies COOL ICE service handler 102 that aservice request has been received and logged in. The service requestitself is utilized by COOL ICE service handler 102 to retrieve apreviously stored sequence of data base management system commandstatements from repository 166. Thus, in the general case, a singleservice request will result in the execution of a number of ordered database management system commands. The exact sequence of these commands isdefined by the service request developer as explained in more detailbelow.

Service input parameters 170 is prepared from the service request itselfand from the command sequence stored in repository 166 as shown by path164. This list of input parameters is actually stored in a dedicatedportion of repository 166 awaiting processing of the service request.

Each command statement from repository 166 identified with the servicerequest is sequentially presented to COOL ICE service 168 for processingvia path 160. The corresponding input parameter from service inputparameters 170 is coupled with each command statement via path 176 toproduce an appropriate query of the enterprise data base managementsystem at COOL ICE service 168. After the enterprise data basemanagement system has responded to a given query, the intermediateproducts are stored as entries in HTML document 172 which is also storedin a dedicated portion of repository 166.

After all command statements corresponding to the service request havebeen processed by the enterprise data base management system and HTMLdocument 172 has been completed, the result is provided via path 156 toCOOL ICE service handler 156 for temporary storage as a browser outputfile in storage resource 154 via path 152. COOL ICE gateway 100 receivesthe browser output file via path 148. The response is converted to HTMLprotocol and transferred by web server 50 and world wide web path 134 tobe presented to the user as a modified screen (not shown).

FIG. 7 is a pictographic drawing 178 of the development process forcreating a COOL ICE service. HTML document 180 is created utilizing anycommercially available standard HTML authoring tool (e.g., MicrosoftFrontPage). The resulting HTML document 180 is stored as a normal HTMfile. This file will be utilized as a template of the service to bedeveloped.

The authoring process moves along path 182 to invoke the administrationmodule of the COOL ICE system at element 184. The new dynamic service iscreated using HTML document 180 stored as a normal HTM file as atemplate. As HTML document 180 is imported into COOL ICE, sequences ofscript for the beginning and end of the HTML code are automaticallyappended to the service. Required images, if any, are also uploaded ontothe web server (see also FIGS. 5 and 6). The service is edited byinserting additional COOL ICE script, as required. A more detaileddescription of the editing process may be found in COOL ICE User'sGuide, Revision 1.1, available from Unisys Corporation and incorporatedherein by reference.

The completed service script is transferred along path 186 to element188 for storage. The service is stored as an object in the repository(see also FIGS. 5 and 6). Storage is effected within the appropriatecategory 190 as discussed above, along with services 192, 194, and 196within the same category.

The process proceeds along path 198 to element 200 for testing. Toperform the testing, the URL for the newly created service is enteredinto the browser of the intemet terminal, if known. The typical URL isas follows:

http://machine-name/ICEGate/Category/Service

If the URL for the new service is not known, a list of the availableservices may be determined from the COOL ICE system by specifying theCOOL ICE URL as follows:

http://machine-name/ICEGate

This call will result in a presentation of a menu containing the definedcategories. Selecting a category from the list will result in a menu forthe services defined within that category. The desired service can thusbe selected for testing. Selection of the service by either means willresult in presentation of the HTML page as shown at element 200.

The process proceeds to element 204 via path 202, wherein the HTML pagemay be enhanced. This is accomplished by exporting the HTML documentfrom the COOL ICE administration module to a directory for modification.By proceeding back to HTML document 180, the exported HTML template isavailable for modification using a standard HTML authoring tool. Aftersatisfactory completion, the finished HTML document is saved for futureuse.

The process developed in this manner is debugged using the debug tooldiscussed below in accordance with the description of FIGS. 10 and 11.Using this debug tool, the user, sitting at an internet terminal, canexecute the developed process under controlled conditions, view theintermediate products, revise the script in accordance with thedescription above, and retest the modified process.

FIG. 8 is a diagram showing a comparison between dialog-based structure210 and service-based structure 212. Dialog-based structure 210 is thenorm for the typical existing proprietary data base management system(e.g., CLASSIC MAPPER). The user, normally sitting at a dedicated userterminal, transfers output screen 214 to the data base management systemto request a service. The user terminal and its normally dedicated linkare suspended at element 216 to permit transfer and operation of thedata base management system. The input is validated at element 218,while the user terminal and its normally dedicated link remainssuspended.

The data base management system processes the service request at element220 while the user terminal remains suspended. Output occurs at element222 thereby releasing the suspension of the user terminal. Thus, a truedialog is effected, because one part of the dialog pair (i.e., the userterminal) is suspended awaiting response from the data base managementsystem. This type of dialog is best accomplished in an environmentwherein at least the user terminal (or data base management system) isdedicated to the dialog, along with the link between user terminal anddata base management system.

Service-based structure 212 illustrates on of the basic constraints ofthe world wide web protocol. To ensure that each of the elements on theworld wide web are sufficiently independent to prevent one element fromunduly delaying or “hanging-up” another element to which it is coupledawaiting a response, the communication protocol forces a terminationafter each transmission. As can be readily seen, even the simplestdialog requires at least separate and independent transactions orservices. The first service, Service 224, involves the transmissions ofoutput form 228 from the intemet user terminal. This transmission isimmediately and automatically followed by termination 230 to ensureindependence of the sender and receiver.

The second service, Service 226, enables the receiver of output form 228to process the request and output an appropriate response. Thevalidation of the input at element 232, processing 234, and output 236all occur within the receiver of output form 228. Immediately andautomatically, termination 238 follows. Thus, if internet transactionsare to be linked into a true dialog to permit data base managementfunctions, the state must be saved from one service to the next astaught herein.

In the preferred mode of the present invention, the state of a serviceis saved in the repository (see also FIGS. 4 and 5) for use in the nextor subsequent services.

FIG. 9 is a schematic diagram 240 of the preferred mode of the presentinvention showing normal data flow during operation, with specialattention to the state saving feature. Work station 242 is an industrycompatible personal computer operating under a commonly availableoperating system such as Windows 95. Browser 92 is a standard,commercially available web browser having frames capability. Path 248 isthe normal world wide web path between work station 242 and web server50 for the transfer of service requests and input data. These transfersare converted by COOL ICE gateway 256 as explained above and sent toCOOL ICE service handler 102 via path 266 for disposition.,

The service request for data and/or another function is converted intothe data base management language by reference to the service definitionportion of repository 262 through reference along path 276. The actualcommand language of the data base management system is utilized overpath 286 to access data base 264. The resultant data from data base 264is transferred to COOL ICE administrator 104 via path 288. State manager260 determines whether the original service request requires additionalqueries to data base 264 for completion of the dialog. If yes, theresultant data just received from data base 264 is transferred via path284 to repository 262 for temporary storage, and the next query isinitiated over path 286, and the process is repeated. This is the statesaving pathway which is required to provide the user of the COOL ICEsystem to function in a dialog form over the world wide web.

Upon receipt of the resultant data from the final query of data base264, state manager 260 determines that the service request is nowcomplete. State manager 260 notifies repository 262 via path 280, andthe intermediate products are retrieved from temporary storage inrepository 262 via path 278 and supplied to COOL ICE service handler 102via path 272 for formatting. State manager 260 then clears theintermediate products from temporary storage in repository 262 via path282. The final response to the service request is sent to COOL ICEgateway 100 via path 270 for translation and to browser 92 via path 250.

FIG. 10 is a detailed diagram 290 showing operation of the debug tool ofthe preferred mode of the present invention as utilized during thedevelopment of a process. A user at work station 292 is interfacing withcommercially available browser 92 to debug server side script which haspreviously been written in accordance with the procedure discussed aboveconcerning FIG. 7. The browser interface via paths 296 and 298 is overthe world wide web.

Server 300, containing COOL ICE system 302, includes COOL ICE service322, which has been written as described above and is to be testedand/or debugged using the COOL ICE debug program 318. COOL ICE service102 is initiated through COOL ICE gateway 100 and the COOL ICE servicehandler via paths 306, 308, 314, and 316 as with the initiation of anyservice (see above). However, upon initiation, the HTML page specifies“Trace” to permit the intermediate products of COOL ICE service 102 tobe extracted, processed, and stored for debug purposes. Therefore, asCOOL ICE service 102 is executed using specially prepared test inputsreceived from the COOL ICE service handler via path 320, all input andoutput data of COOL ICE service 102 is available to the debug programvia path 318 and transferred via path 310 for storage in debug file 312

This debug process can be repeated a number of times to initiateexecution of COOL ICE service 322 using different test data sets. Theresults, stored in debug file 312, may be accessed as described below.FIG. 11 is a view 322 of the windows utilized in referencing the tracelog for debug purposes. The COOL ICE Administration window is calledfrom the COOL ICE home page as described above. Through a call tooptions 334, window 336 is retrieved from storage. Window 336 provides adescription of the trace log, as shown. Entry 350 is a typical entry inthe trace log. Button 338 provides an opportunity to view the entry orentries. Buttons 340, 342, 344, and 346 provide the user with anopportunity to run it, delete it, clear all, or cancel. Button 348 isfor access to help information. In this manner, a service can bedebugged.

Having thus described the preferred embodiments of the presentinvention, those of skill in the art will be readily able to adapt theteachings found herein to yet other embodiments within the scope of theclaims hereto attached.

I claim:
 1. In a data processing environment having a user terminalcoupled to a publicly accessible digital communications network withservice requests in a service-based structure and having a data basemanagement system with service requests including a sequence of scripteddata base management commands, the improvement comprising: a. a servercoupled to said user terminal via said publicly accessible digitalcommunications network and coupled to said data base management systemwherein said server includes a debug program which permits said userterminal to initiate execution of said sequence of scripted data basemanagement commands with prepared test inputs in a trace mode whichstores intermediate and final outputs resulting from said execution ofsaid sequence of scripted data base management commands; b. anadministrative module located within said server wherein said userterminal communicates with said administration module via anAdministration Window which displays a description of a trace logwhereby said user terminal may request information concerning an entryin said trace log; and c. wherein said Administration Window includesbuttons which permit a user at said user terminal to modify said entryin said trace log.
 2. The improvement according to claim 1 wherein saiddebug program includes a debug file for storing said outputs.
 3. Theimprovement according to claim 2 wherein said publicly accessibledigital communications network is the world wide web.
 4. The improvementaccording to claim 3 wherein said user terminal is an industrycompatible personalized computer including a commercially available webbrowser.
 5. The improvement according to claim 4 wherein said data basemanagement system is a proprietary data base management system.
 6. Anapparatus comprising: a. a user terminal; b. a publicly accessibledigital communications network having a service-based request languagecoupled to said user terminal; c. a server coupled to said user terminalvia said publicly accessible digital communications network; d. a database management system having a dialog-based request languageresponsively coupled to said server; e. a debug program located withinsaid server whereby said user terminal can initiate execution of saiddialog-based request language in a debug state which produces a trace f.an administrative module located within said server and coupled betweensaid debug program and said user terminal; g. an administration windowproduced by said administration module which communicates between saiduser terminal and said debug program and which displays a representationof said trace log whereby said user terminal can request informationconcerning an entry in said trace log; h. a button located on saidadministration window which permits a user at said user terminal tomodify said entry in said trace log; and i. wherein said debug programhas a debug file for storage of intermediate products of saiddialog-based request.
 7. The apparatus of claim 6 wherein said userterminal has access to said debug file.
 8. The apparatus of claim 7wherein said publicly accessible digital communications network is theworld wide web.
 9. The apparatus of claim 8 wherein said user terminalis an industry compatible personal computer having a commerciallyavailable web browser.
 10. A method of communicating between a userterminal utilizing service-based data requests and a data basemanagement system employing dialog-based data requests comprising: a.transmitting a debug service-based request from said user terminal; b.initiating execution of an ordered sequence of dialogbased requests inresponse to said debug service-based request from said user terminal; c.executing said ordered sequence of dialog-based requests in a trace modeunder control of a debug program to produce a trace log; d. preparing anadministration window containing a display corresponding to said tracelog; e. sending a signal to said user terminal which presents saidadministration window on said user terminal; f. selecting a particularentry of said trace log from said administration window; g. transferringthe selection from said selecting step to said data base managementsystem; h. accessing information concerning said selection andtransmitting it to said user terminal; and i. utilizing a button on saidadministration window to modify said entry of said trace log from saiduser terminal.
 11. A method according to claim 10 further comprisingstoring results of said executing step in a debug file.
 12. A methodaccording to claim 11 further comprising transferring a copy of saiddebug file to said user terminal.
 13. A method according to claim 12wherein said transmitting step further comprises transmitting over theworld wide web.
 14. A method according to claim 13 wherein said database management system further comprises a proprietary data basemanagement system.
 15. An apparatus comprising: a. means for permittinga user to interact with a digital data base; b. means responsivelycoupled to said permitting means for providing said user with access toa publicly accessible digital communication network via service-basedrequests; c. means responsively coupled to said permitting means foroffering data processing services according to dialog-based requests; d.means responsively coupled to said offering means and said permittingmeans for instituting a trace mode concerning said dialog-based requestsand for creating a trace log; e. means responsively coupled to saidimposing and creating means for preparing an administration windowcorresponding to said trace log; f. means responsively coupled to saidpreparing means for presenting said administration window on saidpermitting means; g. means located within said administration window formodifying said trace log; h. wherein said publicly accessible digitalcommunication network further comprises the world wide web; and i.wherein said converting means further comprises means for storingintermediate products of said dialog-based requests.
 16. An apparatusaccording to claim 15 wherein said offering means further comprises aproprietary data base management system.
 17. An apparatus according toclaim 16 wherein said permitting means further comprises an industrystandard personal computer.